home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
6_1_09.tro
< prev
next >
Wrap
Text File
|
1991-12-13
|
46KB
|
2,226 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright ( c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v | 5i'
.sp 1P
.ce 1000
\v'3P'
SECTION\ 3
.ce 0
.sp 1P
.ce 1000
\fBSUPPLEMENTARY\ SERVICES\fR
.ce 0
.sp 1P
.sp 2P
.LP
\fBRecommendation\ Q.80\fR
.RT
.sp 2P
.ce 1000
\fBINTRODUCTION\ TO\ STAGE\ 2\ SERVICE\ DESCRIPTIONS\fR
.EF '% Fascicle\ VI.1\ \(em\ Rec.\ Q.80''
.OF '''Fascicle\ VI.1\ \(em\ Rec.\ Q.80 %'
.ce 0
.sp 1P
.ce 1000
\fBFOR\ SUPPLEMENTARY\ SERVICES\fR
.ce 0
.sp 1P
.LP
\fB1\fR \fBIntroduction\fR
.sp 1P
.RT
.PP
The purpose of this Recommendation is to provide an introduction to the
Stage\ 2 service descriptions for supplementary services, given in
Recommendations\ Q.81\(hy87.
.RT
.sp 2P
.LP
\fB2\fR \fBCross\(hyreferences\fR
.sp 1P
.RT
.PP
The work in Recommendations\ Q.81\(hy87 is based on the Stage 1 service
descriptions given in the I.251\(hy257\(hySeries Recommendations (see Annex\
A). They are coordinated with the Stage\ 2 service description for basic
calls, given in Recommendation Q.71, and were developed according to the
methodology given in Recommendation\ Q.65.
.RT
.sp 2P
.LP
\fB3\fR \fBRelationships among supplementary services\fR
.sp 1P
.RT
.sp 1P
.LP
3.1
\fICall diversion services\fR
.sp 9p
.RT
.PP
Recommendation I.252, \(sc\(sc 2\(hy5, defines a set of supplementary
services called \*QCall Diversion Services\*U. This set consists of the Call
Forwarding supplementary services and the Call Deflection supplementary
service. This section describes how these services relate to each other and
describes the different network routing techniques which may be used to
provide these services. It begins with the latter topic.
.RT
.sp 1P
.LP
3.1.1
\fINetwork Routing Techniques\fR
.sp 9p
.RT
.PP
Figure 1/Q.80 gives an overview of the Call Diversion services and illustrates
the network routing techniques that may be used for these
services.
.PP
Referring to Figure 1/Q.80, a Call Diversion occurs if User A calls
User\ B who has subscribed to one of the Call Diversion services, and the
call processing for that service (described below) determines that the
call should be sent to User\ C.
.PP
If User C is relatively close to User B, then it would be reasonable for
User B's serving switch to simply switch the call to User\ C (i.e. act
like a transit switch as if User\ A had called User\ C directly). This
technique is
called \*Qforward switching\*U.
.PP
If User C is not close to User B (e.g. User CC in Figure 1/Q.80), then
it might be reasonable for User B's serving switch to ask that a previous
switch in the call path (e.g. Switch\ 2) to re\(hyroute the call. This
is called
\*Q(partial) rerouting\*U. If User\ B's serving switch asks that User A's
switch
(i.e.\ Switch\ 1) re\(hyroute the call, this is called \*Q(full) rerouting\*U.
.bp
.PP
\fINote\ 1\fR \ \(em\ The choice of network routing technique is the prerogative
of each network provider and may be determined by factors other that
geographical distance.
.PP
\fINote\ 2\fR \ \(em\ The analogy to a transit switch is not totaly correct.
In general, User\ A will be charged for the connection to User\ B, and
User\ B will be charged for the connection to User\ C.
.RT
.LP
.rs
.sp 25P
.ad r
\fBFigure 1/Q.80, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
3.1.2
\fICall processing\fR
.sp 9p
.RT
.PP
In Call Forwarding, the decision to divert the call is made by the serving
switch, either because it has been instructed (by a previous
interaction with the served user) to forward all calls, or to forward any
calls that meet busy, or those that meet No Reply. (See Figure\ 2/Q.80).
(Details of the call processing for Call Forwarding are given in Recommendations\
Q.82, \(sc\ 2, \(sc\ 3 and \(sc\ 4).
.PP
In Call Deflection, the decision to divert the call is made by the
served user, upon receipt of an incoming call indication. (\fINote\fR \
\(em\ Care should be taken not to confuse Call Deflection with a possible
architecture for Call Forwarding which places the \*Qforwarding detection\*U
entity in the served user's equipment. In Call Deflection, the actual user
is involved in deciding whether to divert the call). (Details of the call
processing for Call Diversion are
expected to be provided early in the next study period.)
.RT
.LP
.rs
.sp 7P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 30P
.ad r
\fBFigure 2/Q.80, p.\fR
.sp 1P
.RT
.ad b
.RT
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation Q.80)
.sp 9p
.RT
.ce 0
.ce 1000
\fBCross\(hyreference list of Stage 1 and Stage 2\fR
.sp 1P
.RT
.ce 0
.ce 1000
\fBRecommendations on supplementary services\fR
.FS
Parentheses \*Q(\ )\*U around a \(sc of a Recommendation number implies
that the \(sc may not appear in the 1988 CCITT Recommendations.
.FE
.ce 0
.LP
\fIStage\ 2\fR \fIBased on Stage 1 given in:\fR
.sp 1P
.RT
.sp 2P
.LP
\fIQ.80\fR \fIIntroduction to Stage 2 service\fR \fIdescription for supplementary
services\fR
.sp 1P
.RT
.sp 1P
.LP
\fIQ.81\fR \fINumber identification supplementary services\fR \fII.251\fR
.sp 9p
.RT
.LP
\(sc\ 1
Direct dialling in
I.251, \(sc\ 1
.LP
(\(sc\ 2)
Multiple subscriber number
I.251, \(sc\ 2
.LP
\(sc\ 3
CLIP
I.251, \(sc\ 3
.LP
\(sc\ 4
CLIR
I.251, \(sc\ 4
.LP
\(sc\ 5
COLP
I.251, \(sc\ 5
.LP
\(sc\ 6
COLR
I.251, \(sc\ 6
.LP
(\(sc\ 7)
Malicious call ID
(I.251, \(sc\ 7)
.LP
(\(sc\ 8)
Sub\(hyaddressing
(I.251, \(sc\ 8)
.bp
.LP
\fIStage\ 2\fR \fIBased on Stage 1 given in:\fR
.sp 1P
.RT
.sp 1P
.LP
\fIQ.82\fR \fICall offering supplementary services\fR \fII.252\fR
.sp 9p
.RT
.LP
(\(sc\ 1)
Call transfer
I.252, \(sc\ 1
.LP
\(sc\ 2
Call forwarding busy
I.252, \(sc\ 2
.LP
\(sc\ 2
Call forwarding no reply
I.252, \(sc\ 3
.LP
\(sc\ 2
Call forwarding unconditional
I.252, \(sc\ 4
.LP
(\(sc\ 3)
Call deflection
(I.252, \(sc\ 5)
.LP
\(sc\ 4
Line hunting
I.252, \(sc\ 6
.sp 1P
.LP
\fIQ.83\fR \fICall completion supplementary services\fR \fII.253\fR
.sp 9p
.RT
.LP
\(sc\ 1
Call waiting
I.253, \(sc\ 1
.LP
\(sc\ 2
Call hold
I.253, \(sc\ 2
.LP
(\(sc\ 3)
CCBS
(I.253, \(sc\ 3)
.sp 1P
.LP
(\fIQ.84\fR \ )
\fIMultiparty supplementary services\fR
\fII.254\fR
.sp 9p
.RT
.LP
(\(sc\ 1)
Conference calling
I.254, \(sc\ 1
.LP
(\(sc\ 2)
Three\(hyparty
I.254, \(sc\ 2
.sp 1P
.LP
\fIQ.85\fR \fI\*QCommunity of interest\*U supplementary services\fR \fII.255\fR
.sp 9p
.RT
.LP
\(sc\ 1
Closed user group
I.255, \(sc\ 1
.LP
(\(sc\ 2)
ISDN networking services
(I.255, \(sc\ 2)
.LP
Private numbering plan
.sp 1P
.LP
\fIQ.86\fR \fICharging supplementary services\fR \fII.256\fR
.sp 9p
.RT
.LP
\(sc\ 1
Credit card calling
I.256, \(sc\ 1
.LP
\(sc\ 2
Advice of charge
I.256, \(sc\ 2
.LP
(\(sc\ 3)
Reverse charging
(I.256, \(sc\ 3)
.sp 1P
.LP
\fIQ.87\fR \fIAdditional information transfer supplementary services\fR
\fII.257\fR
.sp 9p
.RT
.LP
\(sc\ 1
User\(hyto\(hyuser signalling
I.257, \(sc\ 1
\v'6p'
.sp 2P
.LP
\fBRecommendation\ Q.81\fR
.RT
.sp 2P
.sp 1P
.ce 1000
\fBNUMBER\ IDENTIFICATION\ SUPPLEMENTARY\ SERVICES\fR
.EF '% Fascicle\ VI.1\ \(em\ Rec.\ Q.81''
.OF '''Fascicle\ VI.1\ \(em\ Rec.\ Q.81 %'
.ce 0
.sp 1P
.LP
\fB1\fR \fBDirect dialling in (DDI)\fR
.sp 1P
.RT
.sp 1P
.LP
1.1
\fIDefinition\fR
.sp 9p
.RT
.PP
\fBdirect dialling in (DDI)\fR enables a user to call directly
another user on a ISPBX or other private system without attendant
intervention.
.RT
.sp 2P
.LP
1.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
1.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
A part of the ISDN number, which is significant to the user, is
passed to the user. This supplementary service is based on the use of the
ISDN number and does not include sub\(hyaddressing.
.PP
\fINote\ 1\fR \ \(em\ A similar method to select a terminal on a passive
bus is described in the Stage 1 description of the supplementary service
MSN.
.PP
\fINote\ 2\fR \ \(em\ The caller may or may not find the ISDN number in the
public directory.
.PP
Recommendation E.164 provides the flexibility for Administrations to use
national numbering plans of fixed or variable number lengths. This
flexibility also applies to DDI numbers, i.e.\ even within a given PABX
DDI\ numbers of different lengths may appear.
.bp
.PP
The number of digits used by a PABX supporting the DDI feature is
not necessarily known by their serving local exchange nor by any other
entity of the public network.
.PP
The DDI number (fixed or variable length) is sent en\(hybloc or by
over\(hylap sending from the exchange to the PABX or other private system which
finally
and automatically establishes a connection to the destination without the
assistance of an operator.
.RT
.sp 1P
.LP
1.2.2
\fIQualifications on the applicability to telecommunication\fR
\fIservices\fR
.sp 9p
.RT
.PP
No restrictions.
.RT
.sp 2P
.LP
1.3
\fIDerivation of a functional model\fR (Step 1)
.sp 1P
.RT
.sp 1P
.LP
1.3.1
\fIFunctional model description\fR
.sp 9p
.RT
.PP
Two functional models are used to show the different requirements of\ DDI.
.PP
Functional model 1 represents the situation where DDI is used to
address a terminal on a single ISPBX connected to the public network.
.PP
Functional model 2 describes the situation where DDI is used to
address a terminal within a private network consisting of several\ PBXs.
.PP
Although functional model 1 can be seen as a special application
of model 2 it is preferred to describe the two models independently to show
different situations more clearly.
.RT
.LP
.rs
.sp 12P
.ad r
\fBFigure 1\(hy1/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
1.3.2
\fIDescription of the functional entities\fR
.sp 9p
.RT
.LP
FE1:
Call control agent of the calling user
.LP
FE2:
Call control entity of the calling user
.LP
FE3:
DDI Access control to the private network
(located in the public network)
.LP
FE4:
DDI Service control for the called user and
access control in the private network
.LP
FE5:
Call control agent of the called user
.LP
FE6:
DDI Access control in the private network
.LP
FE7:
DDI Service control in the private network
for the called user.
.sp 1P
.LP
1.3.3
\fIRelationship to basic service\fR
.sp 9p
.RT
.PP
The call setup procedures in the public network are mainly the same as
for the basic service.
.PP
FE1 and FE2 therefore have the same functionality as CCA and CC.
r\d1\uand\ r\d2\ucorrespond to r\d1\uand r\d2\uin the basic service.
.PP
FE3 includes specific functionality of DDI in the relationship
r\d3\u.
.PP
FE4, FE6 and FE7 are entities in a private network that are only
specified here as far as they are influenced by r\d3\u. The same applies for
r\d4\uand\ r\d5\u.
.bp
.RT
.sp 2P
.LP
1.4
\fIInformation flow diagrams\fR (Step 2)
.sp 1P
.RT
.sp 1P
.LP
1.4.1
\fIDiagrams\fR
.sp 9p
.RT
.PP
The diagrams for model 1 are shown in Figure 1\(hy2/Q.81.
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure 1\(hy2/Q.81 \ \
(\*`a l'italienne), p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
1.4.1.1
\fIDiagrams for model 2\fR
.sp 9p
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure 1\(hy3/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
\fINotes to Figures 1\(hy2/Q.81 and 1\(hy3/Q.81\fR
.LP
\fINote\ 1\fR \ \(em\ Optional signalling information which may be used
to acknowledge
seizure and/or for B channel negotiation.
.LP
\fINota\ 2\fR \ \(em\ Optional signalling information which may be used
to indicate
complete address information.
.LP
\fINote\ 3\fR \ \(em\ If not already sent, this signalling information
may be sent to
the originating user to indicate complete address information.
.LP
\fINote\ 4\fR \ \(em\ If the PABX recognizes the receipt of complete address
information, this signalling information may be sent.
.LP
\fINote\ 5\fR \ \(em\ On receipt of complete address information, this
signalling
information may be generated by the sub\(hyPABX. If already sent by
the PABX, it will not be transferred to the originating user.
.LP
\fINote\ 6\fR \ \(em\ Instead of ALTERTING, a CONNECT signalling information
may be
sent directly in case of an automatically responding terminal.
.LP
\fINote\ 7\fR \ \(em\ Optional early switch through backward transmission path.
.sp 1P
.LP
1.4.2
\fIDefinitions\fR
.sp 9p
.RT
.PP
The definitions for ACK, ADDRESS INFO, PROCEEDING, REPORT and SETUP are
the same as for the basic service.
.RT
.sp 1P
.LP
1.4.2.1
\fIMeaning of [PROGRESS]\fR
.sp 9p
.RT
.PP
PROGRESS can be sent from the entity serving the called user to
indicate that sufficient ADDRESS INFO was received to address a user terminal
or access line. It is an unconfirmed information flow.
.RT
.sp 1P
.LP
1.4.2.2
\fIInformation content of [PROGRESS]\fR
.sp 9p
.RT
.PP
B\(hychannel information in r\d3\uif not yet included in a previous
sent information element.
.RT
.sp 1P
.LP
1.5
\fISDL diagrams of functional entities\fR (Step 3)
.sp 9p
.RT
.PP
SDL diagrams are provided for FE3 covering the aspects of both
functional models and giving the relation between\ r\d2\uand\ r\d3\u. FE1
and FE2 are, as said, already covered by the basic procedures so that all
aspects of
DDI, that are relevant for the public network, are covered in these diagrams.
.PP
In the SDL diagrams only those procedures are described that
deviate from the basic procedures.
.RT
.LP
.rs
.sp 15P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1\(hy4/Q.81 (sheet 1 of 3), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1\(hy4/Q.81 (sheet 2 of 3), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1\(hy4/Q.81 (sheet 3 of 3), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
\fINotes to Figure 1\(hy4/Q.81 (sheets 1 to 3)\fR
.LP
\fINote\ 1\fR \ \(em\ Through connection is generally only done when the setup
confirmation is received from the called user. This is described in option\ A.
.LP
In specific national applications through connection may already be
done in an earlier point in time. This is covered in options\ B1 or\ B2 and
requires further considerations.
.LP
\fINote\ 2\fR \ \(em\ Negotiation of a B channel is not necessarily an
independent information flow. It can be combined with the first backward
information flow that is required for call control. This information flow
can be PROGRESS, REPORT (alerting) or SETUP.
.sp 2P
.LP
1.6
\fIFunctional entity actions\fR (Step 4)
.sp 1P
.RT
.sp 1P
.LP
1.6.1
\fISpecific actions in FE3\fR
.sp 9p
.RT
.sp 1P
.LP
1.6.1.1
\fIChannel selection\fR
.sp 9p
.RT
.PP
Negotiation for the selection of a B\(hychannel will be permitted
between the network and the\ PABX. The selection procedure is as
follows:
.RT
.LP
a)
in the SETUP Request, the network will indicate one of the
following:
.LP
1)
channel is indicated, no acceptable alternative; or
.LP
2)
channel is indicated, any alternative is acceptable; or
.LP
3)
any channel is acceptable.
.LP
b)
In cases 1) and 2), if the indicated channel is acceptable
and available, the PABX selects it for the call.
.LP
In case 2), if the PABX cannot grant the indicated channel, it
selects any other available B\(hychannel and identifies that channel in
the first information sent in response to the SETUP Indication.
.LP
In case 3), the PABX selects any available B\(hychannel and
identifies that channel in the first information sent in response to
the SETUP Indication.
.LP
c)
If no channel identification information element is present
in the first response, the B\(hychannel indicated in the SETUP Request
will be assumed.
.LP
If the B\(hychannel indicated in the first response is unacceptable
to the network, it will clear the call.
.LP
d)
When a B\(hychannel has been selected by the PABX that channel
may be connected by the PABX.
.LP
e)
In case 1), if the indicated B\(hychannel is not available, or
in cases\ 2), 3), if no B\(hychannel is available and the PABX cannot
proceed with the offered call, the PABX clears the call.
.PP
The preferred solution for B\(hychannel selection is alternative 1): B\(hychannel
is selected by exchange\ B.
.sp 1P
.LP
1.6.1.2
\fIThrough connection\fR
.sp 9p
.RT
.PP
The general time for through connection in FE3 is, when setup is
confirmed by the called user. This prevents fraudulent use of the connection
without charging.
.PP
As a consequence of this procedure all tones and announcements during call
setup have to be generated in the public network.
.PP
As an alternative some network providers may allow for an early
through connection.
.RT
.sp 2P
.LP
1.6.2
\fISpecific actions in FE6 and FE7\fR
.sp 1P
.RT
.sp 1P
.LP
1.6.2.1
\fIThrough connection\fR
.sp 9p
.RT
.PP
In case of an ISDN terminal or sub\(hyPABX connected to the PABX, the through
connection of the B\(hychannel in the PABX is done with the sending of
SETUP to the terminal/sub\(hyPABX. In the sub\(hyPABX the through connection
is done with the sending of SETUP to the terminal. In the terminal the
through
connection is done at the receipt of CONNECT ACKNOWLEDGE from the
PABX/sub\(hyPABX.
.bp
.PP
In case of an analogue terminal connected to the ISDN
PABX/sub\(hyPABX the through connection of the B\(hychannel in the terminal
is done with the sending of CONNECT to the ISDN PABX/sub\(hyPABX. In the
ISDN
PABX/sub\(hyPABX the through connection is done at the receipt of SETUP
Confirmation from the terminal. Note that this case is for further study.
.RT
.sp 1P
.LP
1.7
\fIAllocation of functional entities to physical locations\fR
.sp 9p
.RT
.PP
The mapping between functional entities and their possible physical locations
is given in the following matrix.
.RT
.ce
\fBH.T. [T1.81]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(60p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Functional entities Scenario FE1 FE2 FE3 FE4 FE5 FE6 FE7
_
.T&
lw(60p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Call to ISPBX TE LE LE NT2 TE \(em \(em
_
.T&
lw(60p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Call to private network TE LE LE \(em TE NT2 NT2
_
.TE
.nr PS 9
.RT
.ad r
\fBTable [T1.81], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 1
.sp 2P
.LP
\fB2\fR \fBMultiple subscriber number\fR
.sp 1P
.RT
.PP
Under study.
.RT
.sp 2P
.LP
\fB3\fR \fBCalling Line Identification Presentation (CLIP)\fR
.sp 1P
.RT
.sp 1P
.LP
3.1
\fIGeneral\fR
.sp 9p
.RT
.PP
\fBcalling line identification presentation (CLIP)\fR is a
supplementary service offered to the called party which provides the calling
party's ISDN number, possibly with sub\(hyaddress information, to the called
party.
.RT
.sp 2P
.LP
3.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
3.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
When CLIP is applicable and activated, the network provides the
called party with the number of the calling party at call setup on all
incoming calls.
.PP
The calling party number may be accompanied by a sub\(hyaddress.
.PP
The network should be capable of transmitting at least 15\ digits
(maximum length of an ISDN number). In addition, if provided by the calling
party, the network should be capable of transmitting a sub\(hyaddress.
The length of the sub\(hyaddress is defined in the relevant Recommendation.
.PP
The network to which the calling party belongs should attempt to
ensure that enough digits are transmitted to enable the called party to
return the call, based on the calling number presented.
.bp
.RT
.sp 1P
.LP
3.2.2
\fISpecific terminology\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
3.2.3
\fIQualifications on the applicability to telecommunication\fR
\fIservices\fR
.sp 9p
.RT
.PP
This supplementary service is applicable to all telecommunication services.
.PP
It is to be noted that in the Telematic services, an exchange of
terminal identification (TID) occurs at a higher layer subsequent to a
successful call establishment.
.PP
For Telematic services this supplementary service shall consist only of
the access number of the calling party and this shall be provided by the
network. For other non\(hyvoice services this supplementary service is
for further study. The presentation of the CLI by Telematic terminals and
by other
non\(hyvoice terminals is for further study.
.RT
.sp 1P
.LP
3.3
\fIDerivation of a functional model\fR
.sp 9p
.RT
.PP
This part of the description is common with the service calling
line identification restriction since this service has some impact on calling
line identification presentation.
.PP
The model used for illustrating the calling line identification
services procedures is given below:
.RT
.LP
.rs
.sp 8P
.ad r
\fBDiagram T1110930\(hy88, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
3.4
\fIInformation flow diagrams\fR
.sp 9p
.RT
.PP
The calling line identity information needed to provide the calling line
identification services is normally carried in the messages used to
establish the call.
.PP
The calling line identity will be delivered to the called party by his
local exchange and/or ISPBX during the call establishment if the calling
line identity is available and presentation is allowed.
.PP
If calling line identity is not available in the destination local
or transit exchange at call request, the exchange may optionally request the
calling line identity from the originating local exchange.
.PP
The specifications of functions for Calling Line Identification
include adaptions for private network implementations (in a full private
network environment) and mobile network implementations. Private
Network/Public ISDN interworking situations are for further study.
.PP
The calling line identity is made up of a number of information
units:
.RT
.LP
\(em
the subscriber's national (ISDN) number, or
.LP
\(em
private network (ISDN) number, or
.LP
\(em
international ISDN number and possibly other indications only
for international calls, or
.LP
\(em
partial number (optional) (Note 1);
.LP
\(em
optionally, sub\(hyaddress information, if explicitly provided
by the calling user;
.LP
\(em
numbering plan identification;
.LP
\(em
type of address.
.bp
.PP
In addition to the calling identity the subscriber may be given
the following information:
.LP
\(em
Presentation indicator (PI) showing:
.LP
a)
presentation allowed, or
.LP
b)
presentation restricted, or
.LP
c)
number not available due to interworking (Note 2)
.LP
\(em
Screening indicator (SI) showing:
.LP
a)
user provided, verified and passed, or
.LP
b)
network provided
.PP
\fINote\ 1\fR \ \(em\ For international calls the partial number may be
the international prefix and the country code. For national calls the partial
number may be the trunk prefix and the area code.
.PP
\fINote\ 2\fR \ \(em\ The technical solutions for the various interworking
arrangements with dedicated networks have not been detailed in this
document.
.RT
.LP
.rs
.sp 38P
.ad r
\fBFigure 3\(hy1/Q.81, p. 11\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 27P
.ad r
\fBFigure 3\(hy2/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
\fINotes to Figures 3\(hy1/Q.8 and 3\(hy2/Q.81\fR
.LP
\fINote\ 1\fR \ \(em\ The information flow contains:
.LP
\(em
no information (should not be permitted for DDI\(hyISPBX in some
networks);
.LP
\(em
part of the subscriber number (extension number, selection on a
passive bus);
.LP
\(em
subscriber number;
.LP
\(em
national number indicators;
.LP
\(em
international number (for mobile application);
.LP
\(em
numbering plan identification;
.LP
\(em
type of address;
.LP
\(em
presentation indicator (optional). Optional: sub\(hyaddress.
.LP
.sp 1
.LP
\fINote 2\fR \ \(em\ The information flow contains:
.LP
\(em
national number;
.LP
\(em
if present: sub\(hyaddress;
.LP
\(em
international number;
.LP
\(em
presentation indicator (allowed/restricted/not available due to
interworking);
.LP
\(em
screening indicator (network provided/subscriber provided,
verified and passed);
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.bp
.LP
\fINote 3\fR \ \(em\ The information flow contains:
.LP
\(em
international number;
.LP
\(em
no information (e.g. presentation restriction)
.LP
\(em
if present: sub\(hyaddress;
.LP
\(em
presentation indicator (allowed/restricted/not available due to
interworking);
.LP
\(em
screening indicator (network provided/subscriber provided,
verified and passed);
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.LP
.sp 1
.LP
\fINote\ 4\fR \ \(em\ The information flow contains:
.LP
\(em
no information;
.LP
\(em
national number (for national calls);
.LP
\(em
international number (for international calls);
.LP
\(em
if present: sub\(hyaddress;
.LP
\(em
presentation indicator (allowed/restricted/not available due to
interworking);
.LP
\(em
screening indicator (network provided/subscriber provided,
verified and passed);
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.LP
.sp 1
.LP
\fINote\ 5\fR \ \(em\ The information flow contains:
.LP
\(em
no information;
.LP
\(em
part of the extension number (e.g. selection on a passive bus);
.LP
\(em
extension number or private network number;
.LP
\(em
optional: sub\(hyaddress;
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.LP
.sp 1
.LP
\fINote\ 6\fR \ \(em\ The information flow contains:
.LP
\(em
extension number or private network number;
.LP
\(em
if present: sub\(hyaddress;
.LP
\(em
presentation indicator (allowed/restricted/not available due to
interworking);
.LP
\(em
screening indicator (network provided/subscriber provided,
verified and passed);
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.LP
.sp 1
.sp 2P
.LP
3.5
\fISDL diagrams for functional entities\fR
.sp 1P
.RT
.sp 1P
.LP
\fIFE2\ \(em\ Determination of the calling line identity\ \(em\ originating
side\fR
.sp 9p
.RT
.PP
The ability of an ISDN component to determine the calling line
identity and if present, the sub\(hyaddress. In public network the calling line
identity is the national ISDN number, in private network the private network
number and in mobile network the international ISDN number.
.RT
.sp 1P
.LP
\fIFE3\ \(em\ Determination of the international calling line identity\fR
.sp 9p
.RT
.PP
The ability of an ISDN component to determine the international
calling line identity and if present, the sub\(hyaddress.
.RT
.sp 1P
.LP
\fIFE4\ \(em\ Determination of the calling line identity\ \(em\ destination
side\fR
.sp 9p
.RT
.PP
The ability of an ISDN component to determine the calling line
identity and if present, the sub\(hyaddress. In some networks the calling line
identity given to an extension user connected to an ISPBX shall include
outgoing prefix if the call is originated or passed through the public
network.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 3\(hy3/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 3\(hy4/Q.81 (sheet 1 of 2), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 3\(hy4/Q.81 (sheet 2 of 2), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 3\(hy5/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
\fINotes to Figure 3\(hy5/Q.81\fR
.LP
\fINote\ A\fR \ \(em\ No information about the identity of the calling
party is sent to
the called party.
.LP
\fINote\ B\fR \ \(em\ Set PI\ \(em\ Presentation restricted, address information
will not be
presented to the called party.
.LP
\fINote\ 1\fR \ \(em\ Presentation may be restricted due to national regulations
or
presentation restriction.
.LP
Presentation restriction may be overridden due to the called party's
category (e.g. police).
.LP
\fINote\ 2\fR \ \(em\ The request option is not supported by private networks
(CL identity is always included). The request option is not defined by
Study Group\ XVIII.
.LP
\fINote 3\fR \ \(em\ In the case where the address information is not available
due to
interworking, only the indicators are presented to the user.
.sp 2P
.LP
3.6
\fIFunctional entity actions\fR
.sp 1P
.RT
.sp 1P
.LP
3.6.1
\fIFunctional entity actions for FE2\fR
.sp 9p
.RT
.LP
\(em
Check if calling line identity is provided from the
user;
.LP
\(em
verify (and complete) calling line identity;
.LP
\(em
set PI and SI;
.LP
\(em
set type of number.
.sp 1P
.LP
3.6.2
\fIFunctional entity actions for FE3\fR
.sp 9p
.RT
.LP
\(em
check if calling line identity may be passed between
Administrations;
.LP
\(em
at the originating side: provide international number;
.LP
\(em
at the destination side: add international prefix.
.sp 1P
.LP
3.6.3
\fIFunctional entity actions for FE4\fR
.sp 9p
.RT
.LP
\(em
check CLIP subscription;
.LP
\(em
check if calling line identity is provided from FE3;
.LP
\(em
request the calling line identity (optional);
.LP
\(em
check for CLIR and if presentation is allowed pass CLI to
FE5.
.LP
.rs
.sp 20P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.sp 1P
.LP
3.7
\fIAllocation of functional entities to physical location\fR
.sp 9p
.RT
.ce
\fBH.T. [T2.81]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
Functional entity Scenario FE1 FE2 FE3 FE4 FE5
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
National call TE LE LE TE
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
International call TE LE TR LE TE
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
Call between NT2s NT2 LE (TR) LE NT2
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
Call between NT2\(hyTE NT2 LE (TR) LE TE
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
National private network TE NT2 NT2 TE
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
International private network TE NT2 TR/NT2 NT2 TE
.TE
.LP
\fINote\fR
\ \(em\ (TR) means that this functional entity is included in the case of
international calls.
.nr PS 9
.RT
.ad r
\fBTable [T2.81], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
.sp 3
\fB4\fR \fBCalling Line Identification Restriction (CLIR)\fR
.sp 1P
.RT
.sp 1P
.LP
4.1
\fIGeneral\fR
.sp 9p
.RT
.PP
\fBcalling line identification restriction (CLIR)\fR is a
supplementary service offered to the calling party to restrict presentation
of the calling party's ISDN number and sub\(hyaddress to the called party.
.RT
.sp 2P
.LP
4.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
4.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
When CLIR is applicable and activated the originating node provides the
destination node with a notification that the calling party's ISDN number
and any sub\(hyaddress information is not allowed to be presented to the
called
party. In this case no calling party number is included in the call offering
to the called party's installation.
.PP
\fINote\fR \ \(em\ When CLIR is subscribed to, some network providers may not
wish to send the originating identity of the calling customer to other
network providers.
.PP
Calling line identification restriction includes two
options:
.RT
.LP
i)
presentation restriction for all calls;
.LP
ii)
temporary presentation restriction.
.PP
The presentation indicator is included in the SETUP req. ind.
Information Flow received from the calling user. When no indicator is present
a default value is used as follows.
.bp
.PP
The presentation indicator is stored in the public network (local
exchange) as a default value for each user. The default value may be
\*Qpresentation allowed\*U or \*Qpresentation restricted\*U. This default
value may be changed \fIonly\fR by the network provider.
.PP
The first option is considered a minimum implementation.
.PP
The second option gives the calling user a possibility on a per
call basis to override the default presentation indicator value stored
in the public network. This option may be available on a subscription basis
or
generally.
.RT
.sp 1P
.LP
4.2.2
\fISpecific terminology\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
4.2.3
\fIQualifications on the applicability to telecommunication\fR
\fIservices\fR
.sp 9p
.RT
.PP
None identified; i.e., this supplementary service is applicable
to all telecommunication services.
.PP
The service calling line identification restriction has impact on the service
calling line identification presentation, and therefore, the rest of
the description is common for the two services. This part is presented
in the CLIP description.
.RT
.sp 2P
.LP
\fB5\fR \fBConnected Line Identification Presentation (COLP)\fR
.sp 1P
.RT
.sp 1P
.LP
5.1
\fIGeneral\fR
.sp 9p
.RT
.PP
\fBconnected line identification presentation (COLP)\fR is a
supplementary service offered to the calling party which provides the connected
party's ISDN\(hynumber to the calling party.
.RT
.sp 2P
.LP
5.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
5.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
When COLP is applicable and activated, the network provides the
calling party with the number of the connected party when the called party
responds positively to the incoming call. The network should be capable of
transmitting at least 15 digits (maximum length of an ISDN number).
.RT
.sp 1P
.LP
5.2.2
\fISpecific terminology\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
5.2.3
\fIQualifications on the applicability to telecommunication\fR
\fIservices\fR
.sp 9p
.RT
.PP
This supplementary service is applicable to all telecommunication services.
.PP
It is to be noted that in the Telematic services, an exchange of
Terminal Identification (TID) occurs at a higher layer subsequent to a
successful call establishment.
.PP
For Telematic services, this supplementary service shall consist only of
the access number of the connected party and this shall be provided by
the network. For other non\(hyvoice services, this supplementary service
is for
further study. The presentation of the COLI by Telematic terminals and
by other non\(hyvoice terminals is for further study.
.RT
.sp 1P
.LP
5.3
\fIDerivation of a functional model\fR
.sp 9p
.RT
.PP
This part of the description is common with the service Connected Line
Identification Restriction (COLR) since this service has some impact on
Connected Line Identification Presentation.
.PP
The model used for illustrating the \*QConnected Line Identification
Services\*U procedures is given in Figure\ 5\(hy1/Q.81 below.
.bp
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure 5\(hy1/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
5.4
\fIInformation flow diagrams\fR
.sp 9p
.RT
.PP
The Connected Line Identity information needed to provide the
Connected Line Identification Services is normally carried in the messages
indicating that the call has been answered.
.PP
The original Connected Line Identity will be delivered to the
calling party by his local exchange and/or ISPBX when the call enters the
active state if the Connected Line Identity is available and presentation is
allowed.
.PP
If Connected Line Identity is not available in the originating local or
transit exchange at call connection time, the exchange may optionally
request the Connected Line Identity from the destination local exchange.
.PP
The specifications of functions for COLP include adaptions for
private network applications (in a full private network environment) and
mobile network applications. Private NetworkB/FPublic ISDN interworking
situations are for further study.
.PP
The Connected Line Identity is made up of a number of information
units:
.RT
.LP
\(em
the subscriber's national (ISDN) number, or
.LP
\(em
private network number, or
.LP
\(em
international ISDN\(hynumber and possibly other indications only
for international calls, or
.LP
\(em
partial number (optional) (Note 1);
.LP
\(em
optionally, sub\(hyaddress information, if explicitly provided
by the calling user;
.LP
\(em
numbering plan identification;
.LP
\(em
type of address.
.PP
In addition to the Connected Line Identity, the subscriber may be given
the following information:
.LP
\(em
Presentation Indicator showing:
.LP
a)
presentation allowed, or
.LP
b)
presentation restricted, or
.LP
c)
number not available due to interworking (Note 2);
.LP
\(em
Screening indicator showing:
.LP
a)
User provided, verified and passed, or
.LP
b)
network provided.
.PP
\fINote\ 1\fR \ \(em\ For international calls, the partial number may be
the international prefix and the country code. For national calls, the
partial
number may be the trunk prefix and the area code.
.PP
\fINote\ 2\fR \ \(em\ The technical solutions for the various interworking
arrangements with dedicated networks have not been detailed in this
Recommendation.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 5\(hy2/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 27P
.ad r
\fBFigure 5\(hy3/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
\fINotes to Figures 5\(hy2/Q.81 and 5\(hy3/Q.81\fR
.LP
\fINote\ 1\fR \ \(em\ The information flow contains:
.LP
\(em
no information (should not be permitted for DDI\(hyISPBX in some
networks);
.LP
\(em
part of the subscriber number (extension number, selection on a
passive bus);
.LP
\(em
subscriber number;
.LP
\(em
national number;
.LP
\(em
international number (for mobile applications);
.LP
\(em
numbering plan identification;
.LP
\(em
type of address;
.LP
\(em
presentation indicator;
.LP
\(em
optional: sub\(hyaddress.
.LP
.sp 1
.LP
\fINote\ 2\fR \ \(em\ The information flow contains:
.LP
\(em
national number;
.LP
\(em
if present: sub\(hyaddress;
.LP
\(em
international number;
.LP
\(em
presentation indicator (allowed/restricted/not available due to
interworking);
.LP
\(em
screening indicator (network provided/subscriber provided,
verified and passed);
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.bp
.LP
\fINote\ 3\fR \ \(em\ The information flow contains:
.LP
\(em
international number;
.LP
\(em
no information (e.g., presentation restriction);
.LP
\(em
if present: sub\(hyaddress;
.LP
\(em
presentation indicator (allowed/restricted/not available due to
interworking);
.LP
\(em
screening indicator (network provided/subscriber provided);
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.LP
.sp 1
.LP
\fINote\ 4\fR \ \(em\ The information flow contains:
.LP
\(em
no information (depending on indicators);
.LP
\(em
national number (for national calls);
.LP
\(em
international number (for international calls);
.LP
\(em
if present: sub\(hyaddress;
.LP
\(em
presentation indicator (allowed/restricted/not available due to
interworking);
.LP
\(em
screening indicator (network provided/subscriber provided,
verified and passed);
.LP
\(em
type of address;
.LP
\(em
numbering plan identification:
.LP
.sp 1
.LP
\fINote\ 5\fR \ \(em\ The information flow contains:
.LP
\(em
no information;
.LP
\(em
part of the extension number (e.g., selection on a passive bus);
.LP
\(em
extension number or private network number;
.LP
\(em
optional: sub\(hyaddress;
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.LP
.sp 1
.LP
\fINote\ 6\fR \ \(em\ The information flow contains:
.LP
\(em
extension number or private network number;
.LP
\(em
if present: sub\(hyaddress;
.LP
\(em
presentation indicator (allowed/restricted/not available due to
interworking);
.LP
\(em
screening indicator (private network provided/user provided,
verified and passed);
.LP
\(em
type of address;
.LP
\(em
numbering plan identification.
.LP
.sp 1
.sp 2P
.LP
5.5
\fISDL diagrams for functional entities\fR
.sp 1P
.RT
.sp 1P
.LP
\fIFE4\ \(em\ Determination of the Connected Line Identity\ \(em\ Destination
side\fR
.sp 9p
.RT
.PP
The ability of an ISDN component to determine the Connected Line
Identity and if present, the sub\(hyaddress. The Connected Line Identity may
contain prefixes. In public network, the Connected Line Identity is the
national ISDN Number, in private network the private Network Number and in
mobile network the International ISDN Number.
.RT
.sp 1P
.LP
\fIFE3\ \(em\ Determination of the International Connected Line Identity\fR
.sp 9p
.RT
.PP
The ability of an ISDN component to determine the International
Connected Line Identity and if present, the sub\(hyaddress.
.RT
.sp 1P
.LP
\fIFE2\ \(em\ Determination of the Connected Line Identity\ \(em\ Originating
side\fR
.sp 9p
.RT
.PP
The ability of an ISDN component to determine the Connected Line
Identity and if present, the sub\(hyaddress. In some networks, the Connected
Line Identity sent to an extension connected to an ISPBX shall contain
the outgoing prefix.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 5\(hy4/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 5\(hy5/Q.81 (sheet 1 of 2), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 5\(hy5/Q.81 (sheet 2 of 2), p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 5\(hy6/Q.81, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
\fINotes to Figure 5\(hy6/Q.81\fR
.LP
\fINote\ A\fR \ \(em\ No information about the connected line. Identity
is sent to the
calling party.
.LP
\fINote\ B\fR \ \(em\ Set IP presentation restricted. Address information
will not be
presented to the calling party.
.LP
\fINote\ 1\fR \ \(em\ Presentation may be restricted or overridden due
to national
regulations or presentation restriction.
.LP
Presentation restriction may be overridden due to the called party's category
(e.g. police).
.LP
\fINote\ 2\fR \ \(em\ The request option is not supported by private networks.
.LP
\fINote\ 3\fR \ \(em\ In the case where the address information is not
available due to
interworking, only the indicators are presented for the user.
.sp 2P
.LP
5.6
\fIFunctional entity actions\fR
.sp 1P
.RT
.sp 1P
.LP
5.6.1
\fIFunctional entity actions for FE2\fR
.sp 9p
.RT
.LP
\(em
check COLP subscription;
.LP
\(em
check if Connected Line is provided;
.LP
\(em
request Connected Line Identify (optional);
.LP
\(em
check for COLR and if presentation allowed, pass COLI to FE1.
.sp 1P
.LP
5.6.2
\fIFunctional entity actions for FE3\fR
.sp 9p
.RT
.LP
\(em
check if Connected Line Identity may be passed between
administrations;
.LP
\(em
at the destination side: provide international number;
.LP
\(em
at the originating side: add international prefix.
.sp 1P
.LP
5.6.3
\fIFunctional entity actions for FE4\fR
.sp 9p
.RT
.LP
\(em
check if Connected Line Identity is provided from the user;
.LP
\(em
verify (and complete) Connected Line Identity;
.LP
\(em
set PI and SI;
.LP
\(em
set type of number.
.sp 1P
.LP
5.7
\fIAllocation of functional entities to physical location\fR
.sp 9p
.RT
.ce
\fBH.T. [T3.81]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
Functional entity Scenario FE1 FE2 FE3 FE4 FE5
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
National call TE LE LE TE
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
International call TE LE TR LE TE
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
Call between NT2s NT2 LE (TR) LE NT2
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
Call between NT2\(hyTE NT2 LE (TR) LE TE
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
National private network TE NT2 NT2 TE
_
.T&
lw(78p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) | cw(30p) .
International private network TE NT2 TR/NT2 NT2 TE
.TE
.LP
\fINote\fR
\ \(em\ (TR) means that this functional entity is included in the case of
international calls.
.nr PS 9
.RT
.ad r
\fBTable [T3.81], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 2P
.LP
\fB6\fR \fBConnected Line Identification Restriction (COLR)\fR
.sp 1P
.RT
.sp 1P
.LP
6.1
\fIGeneral\fR
.sp 9p
.RT
.PP
\fBconnected line identification restriction (COLR)\fR is a
supplementary service offered to the connected party to restrict presentation
of the connected party's ISDN number to the calling party.
.RT
.sp 2P
.LP
6.2
\fIDescription\fR
.sp 1P
.RT
.sp 1P
.LP
6.2.1
\fIGeneral description\fR
.sp 9p
.RT
.PP
When COLR is applicable and activated, the destination node
provides the originating node with a notification that the connected party's
ISDN number is not allowed to be presented to the calling party. In this
case no connected party number is included in the call connected information
to the calling party's installation.
.PP
\fINote\fR \ \(em\ When COLR is subscribed to, some network providers may not
wish to send the identity of the connected customer to other network
providers.
.PP
\fIDetailed descriptions of functions and information flows\fR
.PP
Connected line identification restriction includes two
options:
.RT
.LP
i)
presentation restriction for all calls;
.LP
ii)
temporary presentation restriction.
.PP
The presentation indicator is included in the SETUP conf. resp.
Information Flow received from the called user. When no indicator is present,
then a default value is used as follows.
.PP
The presentation indicator is stored in the public network (local
exchange) as a default value for each user. The default value may be
\*Upresentation allowed\*U or \*Qpresentation restricted\*U. This default
value may be changed \fIonly\fR by the network provider.
.PP
The first option is considered a minimum implementation.
.PP
The second option gives the user who receives (and accepts) the
call, a possibility on a per call basis to override the default presentation
indicator value stored in the public network. This option may be available
on a subscription basis or generally.
.PP
The service connected line identification restriction has impact on
the service connected line identification presentation, and therefore,
the rest of the description is common for the two services. This part is
presented in the COLP description.
.RT
.sp 1P
.LP
6.2.2
\fISpecific terminology\fR
.sp 9p
.RT
.PP
None identified.
.RT
.sp 1P
.LP
6.2.3
\fIQualifications on the applicability to telecommunications\fR
\fIservices\fR
.sp 9p
.RT
.PP
None identified; i.e., this supplementary service is applicable to all
telecommunication services.
.RT
.sp 2P
.LP
\fB7\fR \fBMalicious call identification\fR
.sp 1P
.RT
.PP
Under study.
.RT
.LP
.rs
.sp 10P
.ad r
Blanc
.ad b
.RT
.LP
.bp